Map rendering method and apparatus, computer device, and storage medium

ABSTRACT

Embodiments of this application disclose a map rendering method performed at a terminal. The method includes: transmitting a block request to a native map module of the terminal through a three-dimensional display engine, the block request carrying a block identifier corresponding to a target field of view area; obtaining a block data address based on the block identifier through the native map module, and transmitting the block data address to the three-dimensional display engine; obtaining block data in the target field of view area based on the block data address through the three-dimensional display engine; invoking a target map interface through the native map module, to parse the block data, and generating map mesh data based on data obtained through parsing, the map mesh data including road data and building data; and performing map rendering based on the road data and the building data in the map mesh data.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation application of PCT Patent ApplicationNo. PCT/CN2019/102035, entitled “MAP RENDERING METHOD AND APPARATUS,COMPUTER DEVICE AND STORAGE MEDIUM” filed on Aug. 22, 2019, which claimspriority to Chinese Patent Application No. 201810971215.6, entitled “MAPRENDERING METHOD AND APPARATUS, AND COMPUTER DEVICE” filed on Aug. 24,2018, all of which are incorporated by reference in their entirety.

FIELD OF THE TECHNOLOGY

This application relates to the field of network technologies, and inparticular, to a map rendering method and apparatus, a computer device,and a storage medium.

BACKGROUND OF THE DISCLOSURE

With development of terminal technologies, rendering of a gaminginterface becomes a research focus of display technologies. For example,rendering a map in a mobile game is usually difficult because arendering manner of a game conflicts with a rendering manner of anexisting map component. Consequently, the existing map component cannotbe directly used on a native side for rendering. Therefore, maprendering is usually performed by using the Unity engine in current gameapplications. However, performance of the Unity engine may causestalling and a waste of memory during running, not only affecting ascreen display effect, but also affecting normal running of a game.

SUMMARY

According to various embodiments provided in this application, a maprendering method and apparatus, a computer device, and a non-transitorycomputer-readable storage medium are provided.

The technical solutions are as follows:

According to an aspect, a map rendering method is performed by aterminal having a processor and memory storing a plurality of computerprograms to be executed by the processor, wherein the plurality ofcomputer programs include a three-dimensional display engine, a nativemap module, and a target map interface, the method comprising:

-   -   transmitting, when the three-dimensional display engine receives        a mesh update instruction, a block request to the native map        module through the three-dimensional display engine, the block        request carrying a block identifier corresponding to a target        field of view area;    -   obtaining a block data address based on the block identifier        through the native map module, and returning the block data        address to the three-dimensional display engine;    -   obtaining block data in the target field of view area based on        the block data address through the three-dimensional display        engine;    -   invoking the target map interface through the native map module,        to parse the block data, and generating map mesh data based on        data obtained through parsing, the map mesh data comprising road        data and building data; and    -   performing map rendering based on the road data and the building        data in the map mesh data.

According to an aspect, a terminal is provided. The terminal includes aprocessor and a memory, the memory storing a plurality of computerprograms including a three-dimensional display engine, a native mapmodule, and a target map interface. The plurality of computer programs,when executed by the processor, cause the terminal to perform the methodin the foregoing embodiment.

According to an aspect, a non-transitory computer-readable storagemedium stores a plurality of computer programs including athree-dimensional display engine, a native map module, and a target mapinterface. The plurality of computer programs, when executed by aprocessor of a terminal, cause the terminal to perform the method in theforegoing embodiment.

Details of one or more embodiments of this application are provided inthe following accompany drawings and descriptions. Other features,objectives, and advantages of this application will become apparent fromthe specification, the accompanying drawings, and the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

To describe the technical solutions of the embodiments of thisapplication more clearly, the following briefly introduces theaccompanying drawings required for describing the embodiments.Apparently, the accompanying drawings in the following description showonly some embodiments of this application, and a person of ordinaryskill in the art may still derive other drawings from the accompanyingdrawings without creative efforts.

FIG. 1 is a diagram of an implementation environment of a map renderingmethod according to an embodiment of this application.

FIG. 2 is a diagram of a rendering effect according to an embodiment ofthis application.

FIG. 3 is a flowchart of a map rendering method according to anembodiment of this application.

FIG. 4 is an exemplary diagram of a target field of view rangeimplemented and provided according to an embodiment of this application.

FIG. 5 is an exemplary diagram of a target field of view rangeimplemented and provided according to an embodiment of this application.

FIG. 6 is an exemplary diagram of a target field of view rangeimplemented and provided according to an embodiment of this application.

FIG. 7 is a flowchart of a rendering process according to an embodimentof this application.

FIG. 8 is a schematic structural diagram of a map rendering apparatusaccording to an embodiment of this application.

FIG. 9 is a schematic structural diagram of a map rendering apparatusaccording to an embodiment of this application.

FIG. 10 is a schematic structural diagram of a map rendering apparatusaccording to an embodiment of this application.

FIG. 11 is a block diagram of a computer device 1100 according to anexemplary embodiment.

FIG. 12 is a diagram of an internal structure of a terminal according toan exemplary embodiment of this application.

DESCRIPTION OF EMBODIMENTS

To make objectives, technical solutions, and advantages of thisapplication clearer and more understandable, this application is furtherdescribed in detail below with reference to the accompanying drawingsand the embodiments. It is to be understood that the specificembodiments described herein are merely used for explaining thisapplication, and are not intended to limit this application. All otherembodiments obtained by a person of ordinary skill in the art based onthe embodiments of this application without creative efforts shall fallwithin the protection scope of this application. For convenience ofunderstanding the embodiments of this application, some terms areexplained herein.

Mesh data: During rendering, a mesh represents a drawable entity. Apiece of mesh data includes at least a set of vertex data, and eachvertex may include attributes such as coordinates and a normal vector. Apiece of mesh data may alternatively include a piece of index data usedfor indexing vector data.

Shader: During rendering, the shader is a piece of instruction codeapplied to a graphics processing unit (GPU) and used for instructing theGPU to perform mesh rendering and generation of a rendering result, forexample, calculate vertex transformation and calculate illumination.

FIG. 1 is a diagram of an implementation environment of a map renderingmethod according to an embodiment of this application. Referring to FIG.1 , in the implementation environment, a terminal includes athree-dimensional display engine, a native map module (which may be, forexample, in a form of a link library) of a terminal system, a renderingmodule, and a target map interface. The three-dimensional display enginemay be a three-dimensional display engine that performs display based onapplication logic. For example, the three-dimensional display engine maybe the Unity game engine. As a cross-platform general game engine,C#language is usually used for game logic development of the Unity gameengine. The foregoing three-dimensional display engine may be a C#scriptpart related to game logic, and this part is unrelated to the terminalsystem. The native map module may be a module implemented based on acomputer language such as C++, and may be stored in the terminal systemin a form of a link library, for the three-dimensional display engine toinvoke. The rendering module may be implemented through a GPU, and canperform screen rendering according to mesh data bound by thethree-dimensional display engine or the native map module, to display aninterface on the terminal. The target map interface may be a map API,and is configured to access a target map server, to use any map dataservice provided by the target map server.

A specific triggering relationship may exist between thethree-dimensional display engine and the native map module. That is,when receiving a specific instruction, the three-dimensional displayengine may trigger, through preset processing logic, the native mapmodule to implement a specific step, to implement a rendering processthrough a linkage process between the three-dimensional display engineand the native map module, to achieve a rendering effect shown in FIG. 2.

Based on an implementation environment provided in FIG. 1 , FIG. 3 is aflowchart of a map rendering method according to an embodiment of thepresent disclosure. In this embodiment of the present disclosure, onlyan example in which a native map module is implemented through a targetlink library is used for description. Referring to FIG. 3 , the methodincludes the following steps.

301. A three-dimensional display engine on a terminal receives a meshupdate instruction.

The three-dimensional display engine may be a three-dimensional displayengine provided by a game side, and may obtain relevant display data byreading a game configuration file, to display a gaming interface. Thegame configuration file may be stored on the terminal, or may be storedon a game server, and be read by the terminal by accessing the gameserver.

In this embodiment of this application, the mesh update instruction isan instruction for updating a map mesh. In some embodiments, the meshupdate instruction may be a frame update instruction, that is, aninstruction for updating a to-be-displayed image frame of the terminal.The mesh update instruction may be triggered based on that a playercontrols a virtual object or that a terminal logged in to by a playermoves in the real world.

The foregoing update may be loading mesh data in a current field of viewrange and unloading mesh data outside the field of view range. For somegames with relatively large game scenes, for example, in some games, amap needs to have a size range the same as that of the real world, butbecause a field of view range of a player is limited, when the playermoves on the map, a map part entering the field of view range needs tobe loaded dynamically, and a part outside the field of view range needsto be unloaded dynamically. Therefore, in some games, a map isequidistantly divided into two-dimensional meshes, as a player moves anda field of view range changes, a block in a mesh is dynamically loadedand unloaded.

302. The three-dimensional display engine transmits a block request to atarget link library of a native system of the terminal, the blockrequest carrying a block identifier corresponding to a target field ofview area.

In this embodiment of this application, when a currently displayed imageframe needs to be updated, the three-dimensional display engine mayfirst obtain the block identifier corresponding to the target field ofview area according to current positioning information of the terminal.A block corresponding to the target field of view area may be a block inthe target field of view area. That is, determined blocks indicated bythe block identifier are all located in the target field of view range,and this is, for example, a case shown in FIG. 4 , or at least one partof each of the determined blocks is located in the target field of viewrange, and this is, for example, a case shown in FIG. 5 . The targetfield of view area may match a display area of the terminal in terms ofa size and a shape, and certainly, may alternatively be slightly largerthan the display area of the terminal, so that when a location of a userslightly changes subsequently, display can be performed quickly, toensure continuity of display. That is, the block corresponding to thetarget field of view area may alternatively be a block in the targetfield of view area or an adjacent block in a specific area around thetarget field of view area, the specific area may be an area within aside length of one block, and this is, for example, a case shown in FIG.6 .

For example, the target field of view area may be a circular area withthe positioning information as a center and a preset distance as aradius, to help a user observe geographic situations around when theuser controls a virtual object to rotate. Certainly, the target field ofview area may alternatively be a rectangular area. Certainly, theforegoing target field of view area may be determined in any determiningmanner. A shape of the determined target field of view area may also bedetermined according to user requirements or a system default, and isnot limited in this embodiment of the present disclosure.

For the determined target field of view area, the three-dimensionaldisplay engine may obtain, according to geographic location informationof the real world corresponding to the target field of view area, ablock identifier of a block located in an area indicated by thegeographic location information from the game configuration file. In thegame configuration file, the block identifier and the geographiclocation information may be stored in a corresponding manner, so thatcorresponding block identifiers are accurately obtained according to thedetermined different pieces of geographic location information.

303. The target link library obtains a block data address based on theblock identifier.

The target link library may store a preset splicing formula. The presetsplicing formula may include an address splicing manner of thethree-dimensional display engine service, and after the target linklibrary obtains the block identifier provided by the three-dimensionaldisplay engine, address splicing may be performed on the blockidentifier according to the preset splicing formula, to obtain the blockdata address. Alternatively, the obtaining process of step 303 may beimplemented through the following process: The target link libraryanalyzes the block identifier, to obtain a block data addresscorresponding to each block identifier. With regard to which obtainingmanner is adopted, no limitation is imposed in this embodiment of thisapplication.

304. The target link library transmits the block data address to thethree-dimensional display engine.

305. The three-dimensional display engine obtains block data in thetarget field of view area based on the block data address.

In this embodiment of this application, the three-dimensional displayengine transmits a download request to the target server, the downloadrequest carrying the block data address; and receives the block data inthe target field of view area transmitted by the target server. Thetarget server may be a server providing a map data service for thethree-dimensional display engine.

306. The three-dimensional display engine transmits the block data inthe target field of view area to the target link library.

If the block data is loaded by the three-dimensional display engine, thethree-dimensional display engine needs to process a large volume of datain a centralized manner, resulting in high time overheads. Therefore, inthis embodiment of the present disclosure, this part is transferred to anative target link library of the terminal system for execution, toreduce a workload of the three-dimensional display engine and also avoidimpact on normal running of a game application.

307. Invoke a target map interface to parse the block data in a casethat the target link library receives the block data.

The target map interface is configured for association with a target mapservice, to enable the target link library to invoke the target mapservice through the target map interface, to parse the block data. Thetarget link library usually does not have a capability of parsing blockdata. Therefore, the target map interface may be provided to enable thetarget map service to provide a parsing function, to parse the blockdata, so that the native target link library can participate in arendering process of the three-dimensional display engine, therebygreatly reducing a processing burden of the three-dimensional displayengine during the whole rendering process.

308. The target link library simplifies road data and building data indata obtained through parsing, to obtain the map mesh data.

The data obtained through the foregoing parsing process includes roaddata and building data. Roads may have a complex situation such as abending or an intersection, and because the roads have different sizes,the road data may be simplified, and the simplification may specificallyinclude at least one of the following processes:

-   -   (1) Scale up or down road sizes of the road data to a preset        size, where the preset size may match the display area of the        terminal, or the preset size may be a size preset by the system,        so that the displayed road size may match a size of the display        area of the terminal. Certainly, the preset size may        alternatively be determined according to a scaling operation of        a user on the terminal or a scaling ratio set by the user on the        terminal, which is not limited in this embodiment of the present        disclosure.    -   (2) Simplify intersections in the road data. A processing manner        of the simplification is not limited in this embodiment of the        present disclosure. An objective of the simplification is to        reduce density of lines in the road data, thereby improving        definition of display.    -   (3) Perform dimension reduction on road vertex coordinates in        the road data, to obtain road vertex coordinates represented by        a two-dimensional vector.

In this embodiment of this application, the data obtained throughparsing by the target map interface includes road vertex coordinates andindex data included in the road data. The road vertex coordinates are athree-dimensional vector and are used for representing coordinates ofthe vertex in three dimensions x, y, and z. However, in this embodimentof the present disclosure, a displayed road may not include ups anddowns, and the road only needs to be displayed with an effect of beingpaved on the ground. Therefore, dimension reduction may be performed onthe road vertex coordinates, and road vertex coordinates after thedimension reduction are represented by using a two-dimensional vector.That is, the road vertex coordinates after the dimension reduction onlyneed to have two dimensions x and y.

Further, because three more floating point parameters are needed forgame effect display, based on the road vertex coordinates after thedimension reduction and the three floating point parameters, a vertexmay be represented by using a five-dimensional vector, which, comparedwith being represented in a form of a six-dimensional vector that iscurrently adopted, reduces an amount of processing.

The road data may include data such as lakes, grasslands, and roads, andis not specifically limited in this embodiment of the presentdisclosure.

Moreover, road materials include a shader used in road rendering andparameters needed by the shader, and in this embodiment of the presentdisclosure, are managed by the target link library of the native systemof the terminal. Because dimension reduction has been performed on thevertex, the three-dimensional display engine cannot support data afterthe dimension reduction. Usually, the three-dimensional display enginesupports only a three-dimensional or four-dimensional vector as acoordinate parameter, but in this embodiment of the present disclosure,vertex coordinates have been subjected to dimension reduction to becomea two-dimensional vector. Therefore, the shader needs to be implementedon a native side, and shader parameters also need to be transmittedautonomously by the native side to a rendering side.

The building data may be simplified into building outline data andheight data, so that a final displayed building does not need to be acomplete picture of the building, and only a brief outline needs to bedisplayed, thereby improving rendering efficiency and also greatlyreducing an amount of processed data in the whole processing process.

309. Perform map rendering based on the road data and the building datain the map mesh data.

The rendering process may be performed by an OpenGL device on theterminal, and the OpenGL device may perform rendering according to theroad data and the building data bound by the three-dimensional displayengine and/or the target link library. For a specific renderingprocedure, reference may be made to the process in the followingembodiment and the interaction process shown in FIG. 6 .

In the method provided in this embodiment of this application, throughdata exchange between the target link library and the three-dimensionaldisplay engine, the map mesh data can be processed by the native targetlink library of the system replacing the three-dimensional displayengine, so that the three-dimensional display engine does not need toprocess a large amount of data any more, and would not cause excessivetime overheads, thereby avoiding stalling and a waste of memory duringrunning and greatly improving a screen display effect without affectingnormal running of an application. Particularly, for a functionalcomponent that has implemented map rendering on the native side, in themethod provided in this embodiment, based on a rendering function, arendering function on the native side is added into a renderingprocedure of the three-dimensional display engine, to implement maprendering in a native layer, thereby achieving no-stalling experience.

In the rendering procedure shown in step 309, to make effects ofrendered scenes better and prevent the rendered scenes from overlappingeach other or being affected by other display effects, rendering may beperformed based on the following principle: first rendering, during arendering process, an object having transparency greater than targettransparency, and then rendering an object having transparency less thanthe target transparency. For example, all opaque objects are to berendered before all transparent objects. Because roads are opaqueobjects, a rendering order of the roads is higher, and because buildingsare translucent objects, the buildings are rendered together with othertranslucent objects.

To integrate map rendering into the rendering procedure of thethree-dimensional display engine, a target script is added to a mainscene camera. When the target script is run, if an OnPreRender eventoccurs in the camera, because roads are opaque objects, the terminal mayrender lakes, grasslands, and roads by invoking a road renderinginterface on the native side, and if an OnPostRender event occurs in thecamera, the terminal may render buildings on a map by using a buildingrendering interface on the native side. For specific processes,reference may be made to the procedure in FIG. 7 .

-   1. The three-dimensional display engine clears a background. The    three-dimensional display engine (Unity) clears a screen with a    background color, and in addition, clears a depth buffer and a    stencil buffer. Through the foregoing clearing process, rendering    data, for example, context information of graphics rendering, that    has been loaded previously may be cleared.-   2. The three-dimensional display engine triggers an OnPreRender    event function of a target script on a camera.-   3. The target script of the camera triggers a road rendering    function of a map module on a game side.-   4. Trigger the target link library to perform road rendering.-   5. The target link library sets material data of roads into OpenGL    Context. The material data includes a shader and parameters needed    by the shader.-   6. The target link library transverses all blocks, and binds a road    mesh for a block currently located in a field of view area of the    camera into the OpenGL Context.-   7. After the binding, the target link library notifies the OpenGL    Context of performing drawing.-   8. The three-dimensional display engine renders opaque objects in a    scene (except the roads).-   9. The three-dimensional display engine renders transparent objects    in the scene (except buildings).-   10. The three-dimensional display engine triggers an OnPostRender    event function of the target script on the camera.-   11. The target script on the camera triggers a building rendering    function of the three-dimensional display engine.-   12. The three-dimensional display engine sets building materials    into the OpenGL Context.-   13. The three-dimensional display engine triggers rendering on the    buildings.-   14. The target link library transverses all blocks, and binds mesh    data in building data for the block currently located in the field    of view area of the camera into the OpenGL Context.-   15. After the binding, the target link library notifies the OpenGL    Context of performing drawing.

In the foregoing processes, the target link library binds mesh data inthe road data into context information of graphics rendering, and setsmaterial data in the road data into the context information of thegraphics rendering; and for the building data, the target link librarybinds mesh data in the building data into the context information of thegraphics rendering, and the three-dimensional display engine setsmaterial data in the building data into the context information of thegraphics rendering. In the foregoing processes, rendering of athree-dimensional map can be implemented in the three-dimensionaldisplay engine to replace map rendering of the native sdk, to achievemore complex rendering effects. In addition, a mesh is updated on thenative side of the system, to achieve higher performance and lowermemory occupation.

Further, in this embodiment of this application, the rendering functionis further upgraded and modified, so that when roads are rendered, roadmaterials may be bound by using the target link library, and whenbuildings are rendered, rendering may be performed by using a materialsystem of the three-dimensional display engine. Processing map data bythe target link library is successfully embedded into renderingperformed by the three-dimensional display engine, making it easier toachieve complex rendering effects.

It is to be understood that, the steps of the embodiments of thisapplication are not necessarily performed according to a sequenceindicated by step numbers. Unless explicitly specified in thisapplication, the sequence for performing the steps is not strictlylimited, and the steps may be performed in other sequences. Moreover, atleast some of the steps in each embodiment may include a plurality ofsub-steps or a plurality of stages. The sub-steps or stages are notnecessarily performed at the same moment but may be performed atdifferent moments. The sub-steps or stages are not necessarily performedin sequence, but may be performed in turn or alternately with at leastsome of other steps or sub-steps or stages of the other steps.

In an embodiment, a terminal is further provided, where the terminalincludes a map rendering apparatus, the map rendering apparatus includesmodules, and each module may be entirely or partially implemented byusing software, hardware, or a combination thereof.

FIG. 8 is a structural diagram of a map rendering apparatus according toan embodiment of this application. Referring to FIG. 8 , the apparatusincludes:

a first transmitting module 801, configured to transmit a block requestto a native map module of a terminal system through a three-dimensionaldisplay engine in a case that a mesh update instruction is received, theblock request carrying a block identifier corresponding to a targetfield of view area;

an address obtaining module 802, configured to obtain a block dataaddress based on the block identifier through the native map module;

a second transmitting module 803, configured to transmit the block dataaddress to the three-dimensional display engine;

a block data obtaining module 804, configured to obtain block data inthe target field of view area based on the block data address throughthe three-dimensional display engine;

a parsing module 805, configured to invoke a target map interfacethrough the native map module, to parse the block data, and generate mapmesh data based on data obtained through parsing, the map mesh dataincluding road data and building data; and

a rendering module 806, configured to perform map rendering based on theroad data and the building data in the map mesh data.

In some embodiments, the address obtaining module is configured toperform address splicing on the block identifier according to a presetsplicing formula through the native map module, to obtain the block dataaddress.

In some embodiments, the block data obtaining module is configured to:transmit a download request to a target server through thethree-dimensional display engine, the download request carrying theblock data address; and receive the block data in the target field ofview area transmitted by the target server.

In some embodiments, the parsing module is configured to simplify,through the native map module, the road data and the building data inthe data obtained through parsing, to obtain the map mesh data.

In some embodiments, the parsing module is configured to performdimension reduction on road vertex coordinates in the road data throughthe native map module, to obtain road vertex coordinates represented bya two-dimensional vector.

In some embodiments, the rendering module is configured to: firstrender, during a rendering process, an object having transparencygreater than target transparency, and then render an object havingtransparency less than the target transparency.

In some embodiments, the rendering module is configured to bind meshdata and material data in the road data to context information ofgraphics rendering through the native map module, and bind mesh data inthe building data into the context information of the graphics renderingthrough the native map module, and bind material data in the buildingdata into the context information of the graphics rendering through thethree-dimensional display engine.

FIG. 9 is a structural diagram of a map rendering apparatus according toan embodiment of this application. Referring to FIG. 9 , the apparatusincludes:

a transmitting module 901, configured to transmit a block request to anative map module of a terminal system in a case that a mesh updateinstruction is received, the block request carrying a block identifiercorresponding to a target field of view area;

a receiving module 902, configured to receive a block data addressobtained by the native map module based on the block identifier,

the transmitting module 901 being further configured to obtain blockdata in the target field of view area based on the block data address,and transmit the block data to the native map module, the native mapmodule obtaining map mesh data based on the block data, the map meshdata including road data and building data; and

a rendering module 903, configured to perform map rendering based on theroad data and the building data in the map mesh data in a case that arendering instruction is received.

In some embodiments, the rendering module 903 is configured to setmaterial data in the building data into context information of graphicsrendering through the three-dimensional display engine, a graphicsrendering interface performing map rendering based on the contextinformation of the graphics rendering.

FIG. 10 is a structural diagram of a map rendering apparatus accordingto an embodiment of this application. Referring to FIG. 10 , theapparatus includes:

a receiving module 1001, configured to receive a block requesttransmitted by a three-dimensional display engine, the block requestcarrying a block identifier corresponding to a target field of viewarea;

an obtaining module 1002, configured to obtain a block data addressbased on the block identifier;

a transmitting module 1003, configured to transmit the block dataaddress to the three-dimensional display engine;

the receiving module 1001 being further configured to receive block dataobtained by the three-dimensional display engine based on the block dataaddress;

an invocation module 1004, configured to invoke a target map interfaceto parse the block data;

a generation module 1005, configured to generate map mesh data based ondata obtained through parsing, the map mesh data including road data andbuilding data; and

a rendering module 1006, configured to perform map rendering based onthe road data and the building data in the map mesh data in a case thata rendering instruction is received.

In some embodiments, the rendering module 1006 is configured to set meshdata in the road data into context information of a graphics renderinginterface through the native map module, and bind material data in theroad data into the context information of the graphics renderinginterface; and bind mesh data in the building data into contextinformation of graphics rendering through the native map module, thegraphics rendering interface performing map rendering based on thecontext information of the graphics rendering.

When the map rendering apparatus provided in the foregoing embodimentsperforms map rendering, only division of the foregoing function modulesis used as an example for description. In the practical application, thefunctions may be allocated to and implemented by different functionmodules according to requirements. That is, an internal structure of theapparatus is divided into different function modules, to implement allor some of the functions described above. In addition, the map renderingapparatus provided in the foregoing embodiments and the embodiments ofthe map rendering method belong to one conception. For the specificimplementation process, reference may be made to the method embodiments,and details are not described herein again.

FIG. 11 is a block diagram of a computer device 1100 according to anexemplary embodiment. Referring to FIG. 11 , the computer device 1100includes: a processing component 1122, further including one or moreprocessors, and a memory resource represented by a memory 1132 and usedfor storing an instruction, for example, an application program, thatcan be executed by the processing component 1122. The applicationprogram stored in the memory 1132 may include one or more modules, eachof which corresponds to a set of instructions. In addition, theprocessing component 1122 is configured to execute an instruction, toperform the foregoing map rendering method.

The computer device 1100 may further include: a power supply component1126, configured to perform power supply management of the computerdevice 1100, a wired or wireless network interface 1180, configured toconnect the computer device 1100 to a network, and an input/output (I/O)interface 1158. The computer device 1100 may perform an operation basedon an operating system stored in the memory 1132, for example, WindowsServer™, Mac OS X™, Unix™, Linux™, or FreeBSD™.

FIG. 12 shows a diagram of an internal structure of a terminal accordingto an embodiment. As shown in FIG. 12 , the terminal includes aprocessor, a memory, a network interface, and an input apparatus thatare connected through a system bus and that are included by the computerdevice. The memory includes a non-transitory computer-readable storagemedium and an internal memory. The non-transitory computer-readablestorage medium of the terminal stores an operating system, and mayfurther store a computer-readable instruction. The computer-readableinstruction, when executed by the processor, may cause the processor toperform the map rendering method. The internal memory may also store acomputer-readable instruction, and the computer-readable instruction,when executed by the processor, may cause the processor to perform themap rendering method. The input apparatus may be a touch layer coveringa display screen, or may be a button, a trackball, or a touchpaddisposed on a housing of the computer device, or may be an externalkeyboard, touchpad, mouse, or the like.

A person skilled in the art may understand that, in the structure shownin FIG. 12 , only a block diagram of a partial structure related to asolution in this application is shown, and does not constitute alimitation on the terminal to which the solution in this application isapplied. Specifically, the terminal may include more components or fewercomponents than those shown in the figure, or some components may becombined, or a different component deployment may be used.

In an embodiment, the map rendering apparatus provided in thisapplication may be implemented in a form of a computer-readableinstruction, and the computer-readable instruction may be run on theterminal shown in FIG. 12 , The memory of the terminal may store variousprogram modules constituting the map rendering apparatus, for example, afirst transmitting module 801, an address obtaining module 802, a secondtransmitting module 803, a block data obtaining module 804, a parsingmodule 805, and a rendering module 806. A computer-readable instructionformed by the program modules causes the processor to perform the stepsin the map rendering method in the embodiments of this applicationdescribed in this specification.

An embodiment of this application provides a computer-readable storagemedium, storing a computer-readable instruction, the computer-readableinstruction being loaded and executed by a processor to performoperations performed in the map rendering method according to theforegoing embodiments.

A person of ordinary skill in the art may understand that all or some ofthe processes of the methods in the foregoing embodiments may beimplemented by a computer program instructing relevant hardware. Theprogram may be stored in a non-volatile computer-readable storagemedium. When the program runs, the procedures of the foregoing methodembodiments are included. Any reference to the memory, storage, adatabase, or other media used in the embodiments provided in thisapplication may include a non-volatile and/or volatile memory. Thenon-volatile memory may include a read-only memory (ROM), a programmableROM (PROM), an electrically programmable ROM (EPROM), an electricallyerasable programmable ROM (EEPROM), or a flash. The volatile memory mayinclude a random access memory (RAM) or an external cache. As anillustration instead of a limitation, the RAM is available in aplurality of forms, such as a static RAM (SRAM), a dynamic RAM (DRAM), asynchronous DRAM (SDRAM), a double data rate SDRAM (DDRSDRAM), anenhanced SDRAM (ESDRAM), a synchronous link (Synchlink) DRAM (SLDRAM), aRambus direct RAM (RDRAM), a direct Rambus dynamic RAM (DRDRAM), and aRambus dynamic RAM (RDRAM).

After considering the specification and practicing this applicationdisclosed herein, a person skilled in the art would easily conceive ofother implementations of this application. This application is intendedto cover any variation, use, or adaptive change of this application. Thevariations, uses, or adaptive changes follow the general principles ofthis application and include common general knowledge or commontechnical means in the art that are not disclosed in this application.The specification and the embodiments are merely considered as examples,and the actual scope and the spirit of this application are pointed outby the following claims,

It is to be understood that this application is not limited to theaccurate structures that are described in the foregoing and that areshown in the accompanying drawings, and modifications and changes may bemade without departing from the scope of this application. The scope ofthis application is limited by the appended claims only.

What is claimed is:
 1. A map rendering method, performed by a terminalhaving a processor and memory storing a plurality of computer programsto be executed by the processor, wherein the plurality of computerprograms include a three-dimensional display engine, a native mapmodule, and a target map interface, the method comprising: transmitting,when the three-dimensional display engine receives a mesh updateinstruction, a block request to the native map module through thethree-dimensional display engine, the block request carrying a blockidentifier corresponding to a target field of view area; obtaining ablock data address based on the block identifier through the native mapmodule, and returning the block data address to the three-dimensionaldisplay engine; obtaining block data in the target field of view areabased on the block data address through the three-dimensional displayengine; invoking the target map interface through the native map module,to parse the block data, and generating map mesh data based on dataobtained through parsing, the map mesh data comprising road data andbuilding data; and performing map rendering based on the road data andthe building data in the map mesh data.
 2. The method according to claim1, wherein the obtaining a block data address based on the blockidentifier through the native map module comprises: performing addresssplicing on the block identifier according to a preset splicing formulathrough the native map module, to obtain the block data address.
 3. Themethod according to claim 1, wherein the obtaining block data in thetarget field of view area based on the block data address through thethree-dimensional display engine comprises: transmitting a downloadrequest to a target server through the three-dimensional display engine,the download request carrying the block data address; and receiving theblock data in the target field of view area transmitted by the targetserver.
 4. The method according to claim 1, wherein the generating mapmesh data based on data obtained through parsing comprises: simplifying,through the native map module, the road data and the building data inthe data obtained through parsing, to obtain the map mesh data.
 5. Themethod according to claim 4, wherein the simplifying, through the nativemap module, the road data and the building data in the data obtainedthrough parsing, to obtain the map mesh data comprises: performingdimension reduction on road vertex coordinates in the road data throughthe native map module, to obtain road vertex coordinates represented bya two-dimensional vector.
 6. The method according to claim 1, whereinthe performing map rendering based on the road data and the buildingdata in the map mesh data comprises: first rendering an object havingtransparency greater than target transparency, and then rendering anobject having transparency less than the target transparency.
 7. Themethod according to claim 6, wherein the first rendering an objecthaving transparency greater than target transparency, and then renderingan object having transparency less than the target transparencycomprises: binding mesh data in the road data to context information ofgraphics rendering through the native map module, and setting materialdata in the road data into the context information of the graphicsrendering; and binding mesh data in the building data into the contextinformation of the graphics rendering through the native map module, andsetting material data in the building data into the context informationof the graphics rendering through the three-dimensional display engine.8. A terminal, comprising a processor and a memory, the memory storing aplurality of computer programs including a three-dimensional displayengine, a native map module, and a target map interface, the pluralityof computer programs, when executed by the processor, causing theterminal to perform a plurality of operations including: transmitting,when the three-dimensional display engine receives a mesh updateinstruction, a block request to the native map module through thethree-dimensional display engine, the block request carrying a blockidentifier corresponding to a target field of view area; obtaining ablock data address based on the block identifier through the native mapmodule, and returning the block data address to the three-dimensionaldisplay engine; obtaining block data in the target field of view areabased on the block data address through the three-dimensional displayengine; invoking the target map interface through the native map module,to parse the block data, and generating map mesh data based on dataobtained through parsing, the map mesh data comprising road data andbuilding data; and performing map rendering based on the road data andthe building data in the map mesh data.
 9. The terminal according toclaim 8, wherein the obtaining a block data address based on the blockidentifier through the native map module comprises: performing addresssplicing on the block identifier according to a preset splicing formulathrough the native map module, to obtain the block data address.
 10. Theterminal according to claim 8, wherein the obtaining block data in thetarget field of view area based on the block data address through thethree-dimensional display engine comprises: transmitting a downloadrequest to a target server through the three-dimensional display engine,the download request carrying the block data address; and receiving theblock data in the target field of view area transmitted by the targetserver.
 11. The terminal according to claim 8, wherein the generatingmap mesh data based on data obtained through parsing comprises:simplifying, through the native map module, the road data and thebuilding data in the data obtained through parsing, to obtain the mapmesh data.
 12. The terminal according to claim 11, wherein thesimplifying, through the native map module, the road data and thebuilding data in the data obtained through parsing, to obtain the mapmesh data comprises: performing dimension reduction on road vertexcoordinates in the road data through the native map module, to obtainroad vertex coordinates represented by a two-dimensional vector.
 13. Theterminal according to claim 8, wherein the performing map renderingbased on the road data and the building data in the map mesh datacomprises: first rendering an object having transparency greater thantarget transparency, and then rendering an object having transparencyless than the target transparency.
 14. The terminal according to claim13, wherein the first rendering an object having transparency greaterthan target transparency, and then rendering an object havingtransparency less than the target transparency comprises: binding meshdata in the road data to context information of graphics renderingthrough the native map module, and setting material data in the roaddata into the context information of the graphics rendering; and bindingmesh data in the building data into the context information of thegraphics rendering through the native map module, and setting materialdata in the building data into the context information of the graphicsrendering through the three-dimensional display engine.
 15. Anon-transitory computer-readable storage medium storing a plurality ofcomputer programs including a three-dimensional display engine, a nativemap module, and a target map interface, the plurality of computerprograms, when executed by a processor of a terminal, causing theterminal to perform a plurality of operations including: transmitting,when the three-dimensional display engine receives a mesh updateinstruction, a block request to the native map module through thethree-dimensional display engine, the block request carrying a blockidentifier corresponding to a target field of view area; obtaining ablock data address based on the block identifier through the native mapmodule, and returning the block data address to the three-dimensionaldisplay engine; obtaining block data in the target field of view areabased on the block data address through the three-dimensional displayengine; invoking the target map interface through the native map module,to parse the block data, and generating map mesh data based on dataobtained through parsing, the map mesh data comprising road data andbuilding data; and performing map rendering based on the road data andthe building data in the map mesh data.
 16. The non-transitorycomputer-readable storage medium according to claim 15, wherein theobtaining a block data address based on the block identifier through thenative map module comprises: performing address splicing on the blockidentifier according to a preset splicing formula through the native mapmodule, to obtain the block data address.
 17. The non-transitorycomputer-readable storage medium according to claim 15, wherein theobtaining block data in the target field of view area based on the blockdata address through the three-dimensional display engine comprises:transmitting a download request to a target server through thethree-dimensional display engine, the download request carrying theblock data address; and receiving the block data in the target field ofview area transmitted by the target server.
 18. The non-transitorycomputer-readable storage medium according to claim 15, wherein thegenerating map mesh data based on data obtained through parsingcomprises: simplifying, through the native map module, the road data andthe building data in the data obtained through parsing, to obtain themap mesh data.
 19. The non-transitory computer-readable storage mediumaccording to claim 18, wherein the simplifying, through the native mapmodule, the road data and the building data in the data obtained throughparsing, to obtain the map mesh data comprises: performing dimensionreduction on road vertex coordinates in the road data through the nativemap module, to obtain road vertex coordinates represented by atwo-dimensional vector.
 20. The non-transitory computer-readable storagemedium according to claim 15, wherein the performing map rendering basedon the road data and the building data in the map mesh data comprises:first rendering an object having transparency greater than targettransparency, and then rendering an object having transparency less thanthe target transparency.